Troubleshooting the Workflow Web Service

business processes

The Workflow Web Service allows the Laserfiche client application to connect to the Workflow Server, allowing business processes to interact with the Laserfiche repository.

Note: The Workflow Web Service can be edited from the Workflow Configuration Manager or from the Workflow Web Service node in the Workflow Administration Console.

Troubleshooting the Workflow Web Service

• Installation: Ensure the Workflow Web Service was installed during the Workflow installation. Problems may arise during the Workflow installation if ASP.NET is not installed or if ASP.NET is not registered to IIS (this results in error 500.21). Learn more about Workflow software requirements.
• Configuration: In the Workflow Configuration Manager, click the Test link to test the Workflow web application directory. A dialog box will confirm a successful connection.
• Authentication: The Workflow Web Service only supports Anonymous Authentication. If the Workflow Web Service is installed, this authentication is automatically set in the Workflow Configuration Manager.
• IIS: If you make certain configuration changes or encounter a problem in which the Workflow Web Service becomes unavailable, you may need to reset IIS.
• Firewall: Certain firewall settings may block inbound traffic on the port you are using for the Workflow Web Service. Workflow will attempt to detect Windows Firewall; however, all others must be manually configured.

Note: If you suspect you are having issues with a Windows Firewall, try adjusting your firewall settings to allow inbound http traffic.

• Protocols and Ports: The first time the Workflow Web Service is configured, Workflow will automatically create a Workflow Web Service URL based on the name of the machine the Workflow Web Service is installed on. If the default port or protocol for the Workflow Web Service is changed in IIS, then the Workflow Web Service URL must be manually configured to reflect those changes. The default protocol and port settings are as follows:
  • Protocol: The default website bindings can be set to either "http" or "https." Each of these uses a different port.
  • Port: By default, "http" corresponds with port 80 and "https" corresponds with port 443.

  If the protocol or port was modified since the first time the Workflow Web Service was configured, place the new port's number after the Workflow Web Service machine's name in the URL: http://WorkflowWebServiceMachine:PortNumber/Workflow. Republish any business processes that use that Workflow Web Service.

  Example: The first time the Workflow Web Service is configured for a machine named "WorkflowWebServiceMachine," the URL will be: http://WorkflowWebServiceMachine/Workflow. Later, the default port for the "http" protocol is changed to 81 in IIS; the URL must be manually updated as well: https://WorkflowWebServiceMachine:81/Workflow.

• Workflow Server port changes: If the Workflow Server's port changes, you must update the port in Workflow Web Service's configuration file. If you don't update the port, unknown errors occur when launching business processes.

See an example of the error.

Error Code: 0
Error Message: Error launching Business Process:
Entry: Test
Error Type: Unknown Error
Error Message: Connection to the Workflow Server 'localhost' could not be created.

1. Open the following path: Laserfiche\Laserfiche Workflow 9\Web\Laserfiche.Workflow.Web\Config.

2. Open the Config.xml file and change the Connection WorkflowServer attribute to the port that your Workflow Server is using. Show me.